Aerial roof estimation systems and methods

ABSTRACT

Methods and systems for roof estimation are described. Example embodiments include a roof estimation system, which generates and provides roof estimate reports annotated with indications of the size, geometry, pitch and/or orientation of the roof sections of a building. Generating a roof estimate report may be based on one or more aerial images of a building. In some embodiments, generating a roof estimate report of a specified building roof may include generating a three-dimensional model of the roof, and generating a report that includes one or more views of the three-dimensional model, the views annotated with indications of the dimensions, area, and/or slope of sections of the roof. This abstract is provided to comply with rules requiring an abstract, and it is submitted with the intention that it will not be used to interpret or limit the scope or meaning of the claims.

BACKGROUND

1. Field of the Invention

This invention relates to systems and methods for estimatingconstruction projects, and more particularly, to such systems andmethods that allow estimates involving roofs on buildings to be createdremotely.

2. Description of the Related Art

The information provided below is not admitted to be part of the presentinvention, but is provided solely to assist the understanding of thereader.

Homeowners typically ask several roofing contractors to provide writtenestimates to repair or replace a roof on a house. Heretofore, thehomeowners would make an appointment with each roofing contractor tovisit the house to determine the style of roof, take measurements, andto inspect the area around the house for access and cleanup. Using thisinformation, the roofing contractor then prepares a written estimate andthen timely delivers it to the homeowner. After receiving severalestimates from different rooting contractors, the homeowner then selectsone.

There are factors that impact a roofing contractor's ability to providea timely written estimate. One factor is the size of the roofcontractor's company and the location of the roofing jobs currentlyunderway. Most roof contractors provide roofing services and estimatesto building owners over a large geographical area. Larger roofcontractor companies hire one or more trained individuals who travelthroughout the entire area providing written estimates. With smallerroofing contractors, the owner or a key trained person is appointed toprovide estimates. With both types of companies, roofing estimates arenormally scheduled for buildings located in the same area on aparticular day. If an estimate is needed suddenly at a distant location,the time for travel and the cost of commuting can be prohibitive. If theroofing contractor is a small company, the removal of the owner or keyperson on a current job site can be time prohibitive.

Another factor that may impact the roofing contractor's ability toprovide a written estimate is weather and traffic.

Recently, solar panels have become popular. In order to install solarpanels, the roof's slope, geometrical shape, and size as well as itsorientation with respect to the sun all must be determined in order toprovide an estimate of the number and type of solar panels required.Unfortunately, not all roofs on a building are proper size, geometricalshape, or orientation for use with solar panels.

SUMMARY

These and other objects are met by the system and method disclosedherein that allows a company that needs the sizes, dimensions, slopesand orientations of the roof sections on a building in order to providea written estimate. A roof estimation system (“RES”) that practices atleast some of the techniques described herein may include a roofestimating software program and a location-linked, image file database.During use, the physical address or location information of a buildingis provided to the program, which then presents aerial images of roofsections on the building at the specific address location. An overheadaircraft, a balloon, or satellite may produce the aerial images. Animage analysis and calibration is then performed either manually and/orvia a software program that determines the geometry, the slopes, thepitch angles, and the outside dimensions of the roof sections. Theimages may also include the land surrounding the roof sections andbuilding which the estimating company can use to factor in additionalaccess or clean-up costs.

In a first embodiment of the roof estimation system, a roof estimationservice is contacted by a potential customer requesting an estimate forrepair or replacement of a roof on a building. The roof estimationservice uses a local computer with an estimating software program loadedinto its working memory to access an image file database located on thecomputer or on a remote server connected via a wide area network to thelocal computer. The image file database contains image files of variousbuildings. When a request for an estimate is received from a potentialcustomer, the roof estimation service enters the customer's address intothe software program and aerial images of the building are thenpresented to the roof estimation service. The roof estimation servicethen manually measures or uses a roof estimation software program todetermine the slopes, dimensions, and other relevant geometricinformation of the roof sections on the buildings. From thesedeterminations, the overall shape, slopes and square footage of the roofsections are determined and a report is produced. After the report hasbeen prepared, the images are reviewed again for special access andcleanup tasks which can be added to the final estimate beforetransmission to the potential customer.

In another embodiment, the roof estimate software program and image filedatabase, operated by a roof estimation service, are both stored on oneor more a remote computers and accessed by a roof company, via a widearea network. The roof company uses an assigned user name and passwordto log onto the Web site and accessed the computer. After logging on,the roof company submits an address of a building, other relevant jobrelated information, and a request for a report from the roof estimationservice. The roof estimation service associated with the Web site usesthe address information to obtain the images of the roof sections on thebuilding(s) and uses the roof estimation software program andcalibration module to determine the relevant geometry, pitch angles,dimensions, and surface areas of the building's roof. The roofestimation service then produces and sends a report to the roof company.The roof company then uses the report to prepare a final estimate thatis then delivered to its potential customer.

In another embodiment, a roof estimating Web site is created designed toreceive requests for roof estimates directly from potential customers ina region. The roof estimation service that operates the Web site isassociated with various roof companies that provide roof-relatedservices in the region serviced by the Web site. When a potentialcustomer contacts the Web site and requests an estimate for a roofrepair, replacement or installation of equipment, the potential'scustomer's name, address, and contact information is first submitted onthe Web site. The estimation service representative enters the addressof the building into the roof estimation software program. The aerialimages of the buildings are then obtained and analyzed by the servicerepresentative to extract the relevant geometric information about thestructures. A report containing the geometric information obtained fromthe aerial images and other relevant project related informationsupplied by the potential customer are transmitted to roof companiesassociated with the estimation service. The roof company reviews theinformation then prepares an estimate which then can be uploaded to theroof estimating Web site server which then forwards the estimate to thepotential customer, or sent from the roof company directly via email,fax or mail to the potential customer.

In another embodiment, a roof estimation service associated with theroof estimate Web site uses the image file database and roof estimatesoftware to preemptively calculate and store the dimensions, areas,pitch angles, and other relevant geometric information about thebuildings and structures located within a geographic region. Thispre-calculated information can then be used by any of the previouslymentioned embodiments to accelerate the process of obtaining roofestimates within that geographic region.

It should be understood, that the systems and methods described hereinmay be used by any individual or company that would find the calculationof the size, geometry, pitch and orientation of the roof of a buildingfrom aerial images of the building useful. Such companies may includeroofing companies, solar panel installers, roof gutter installers,awning companies, HVAC contractors, general contractors, and insurancecompanies.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration showing embodiments of a system and method forroof estimation.

FIG. 2 is an illustration showing another embodiment of a system andmethod for roof estimation.

FIG. 3 is an illustration showing the top and perspective view of ahouse for a particular address.

FIG. 4 is an aerial image of the home shown in FIG. 3 showing the areasand structures around the home.

FIGS. 5A-5F are consecutive pages from a preliminary or final reportsent to a potential customer prepared by the roofing company.

FIG. 6 is a block diagram illustrating example functional elements ofone embodiment of a roof estimation system.

FIG. 7 is an example block diagram of a computing system for practicingembodiments of a roof estimation system.

FIG. 8 is an example flow diagram of a first example roof estimationroutine provided by an example embodiment.

FIG. 9 is an example flow diagram of a second example roof estimationroutine provided by an example embodiment.

DETAILED DESCRIPTION

Referring to the accompanying Figures, there is described a roofestimation system (“RES”) 10 and method that allows a roof estimationservice 70 to provide a final estimate 102 to a potential customer 90 toinstall equipment or to repair or replace the roof on a building 92using aerial images of the building 92, as shown in FIG. 1. The roofestimation service 70 may be any service that provides roof estimates tocustomers. In one embodiment, the roof estimation service 70 typicallyprovides roof estimates to customers who are roof companies or otherentities involved in the construction and/or repair of roofs, such asbuilders, contractors, etc. In another embodiment, the roof estimationservice 70 is a roof company that is directly involved in theconstruction and/or repair of roofs, and that provides estimates tocustomers that are property owners, general contractors, etc. The system10 includes an estimating software program 50 designed to receive anaddress for the building 92. The software program 50 is linked to anaerial image file database 52 that contains aerial images files 54 ofvarious building 92 in a region. The aerial image files 54 may be takenany available means, such as a manned or unmanned aircraft, a balloon, asatellite, etc. In some embodiments, the aerial image files may includeimages taken from a ground-based platform, such as a mobile (“streetview”) photography vehicle, a fixed position (e.g., a tower, nearbybuilding, hilltop, etc.), etc. As shown in FIG. 3, the image files 54typically include at least one a top plan view 65 and a perspective view66 of the building 92. The roof of the building 92 includes multipleplanar roof sections 92 a-92 d.

As shown in FIG. 4, the image files 54 may also include a wide angleimage 67 showing the building 92 and the surrounding areas 93 around thebuilding 92.

Referring back to FIG. 1, in one embodiment, an image analysis andcalibration module 56 is linked to the software program 50 that enablesthe roof estimation service 70 to closely estimate the dimensions andslopes of the roofs of the buildings 92 shown in the views 65, 66. Bysimply inputting the customer's address into the software program 50,the roof estimation service 70 is able view the customer's roof from theaerial image files 54 using a remote computer 72, determine thedimensions and slopes of the roof sections that make up the roof, andprepare a preliminary report 101 which is then used to prepare a finalestimate 102 that is then delivered to the potential customer 90.

FIG. 1 is an illustration showing the system 10 used by a potentialcustomer 90 requesting a roof estimate from a roof estimation service 70that uses the system 10 described above. The potential customer 90 maybe the building tenant, owner or insurance company. The roof estimationservice 70 uses a computer 72 which may connect to a wide area network60. The customer 90 contacts the roof estimation service 70 via his orher computer 91 and the wide area network 60 or by a telecommunicationnetwork 96, and requests a roof estimate 100 for his building 92 locatedat a public address 93. (in this example, “123 W. 3rd St.”). The roofestimation service 70 then processes the request 100 which leads to afinal estimate 102 being delivered to the potential customer's computer91 or via email, fax or postal service to the potential customer 90.

There are several different ways the system 10 can be setup. FIG. 1shows a first embodiment of the system 10 where the roof estimationservice 70 operates a remote computer 72 with a display 74 and akeyboard 75 or similar input means, such as a mouse, joystick, trackpad, etc. A roof estimating software program 50 is loaded into theworking memory 73 of the remote computer 72. The software program 50 isable to retrieve aerial images of buildings from the database 52containing aerial images files 54 of buildings located in the regionserved by the roof estimation service 70. In the first embodiment shownin FIG. 1, the remote computer 72 is linked or connected to a database52 containing aerial images files 54 of the buildings. The softwareprogram 50 includes a calibration module 56 that enables the roofestimation service 70 to determine the angles and dimensions of variousroof sections shown in the images files 54. After the angles anddimensions are determined, the combined square footage of the building92 can be determined which is then used to create a preliminary report101. The roof estimation service 70 then reviews the wide angle imagefile 67 (see FIG. 4) to determine if the building 92 has special accessand clean up factors that may impact the final estimate 102. Once thepreliminary report 101 or the final estimate 102 is prepared by the roofestimation service 70, one or both can be transmitted to the customer 90via the wide area network 60, the telecommunication network 96, or bypostal service.

Also shown in FIG. 1 is an alternative setup of the system 10 wherein apreliminary report 101 is prepared by a separate roof estimating entity105 which is then forwarded to the roof estimation service 70 who thenprepares the final estimate 102 and sends it to the customer 90. Theentity 105 includes a computer 106 with a roof estimating softwareprogram 50′ loaded into the working memory 107. Like the softwareprogram 50 loaded into the roof contractor's computer 72 in the previousembodiment the software program 50′ is also able to retrieve aerialimages of houses from a database 52′ containing aerial images files 54′of houses located in the region served by the roof estimation service70. An optional calibration module 56′ may be provided which enables theentity 105 to determine the angles and linear dimensions of various roofsections on the house 92.

When the system 10 is set up to include the estimating entity 105, thecustomer 90 may first contact the roof estimation service 70. The roofestimation service 70 may then contact the estimating entity 105 andforward the address of the building 92 thereto. The estimating entity105 may then prepare the preliminary report 101 that is transmitted tothe roof estimation service 70. The roof estimation service 70 may thenprepare the final report 102 and send it to the customer 90. In otherembodiments, interactions between the customer 90, the roof estimationservice 70, and the estimating entity 105 may occur in different waysand/or orders. For example, the customer 90 may contact the estimatingentity 105 directly to receive a final report 102, which the customer 90may then forward to one or more roof companies of their choosing.

FIG. 2 shows a third embodiment of the system 10 where the customer 90contacts a roof estimating entity 130 who receives a request 100 fromthe customer 90 via the wide area network 60 or telecommunicationnetwork 96. The roof estimating entity 130 prepares a preliminary report101 which is then transmitted to various roof estimation services 70,70′, 70″ associated with the entity 130. Accompanying the preliminaryreport 101 may be the name and contact telephone number(s) or emailaddress of the customer 90. Each roof estimation service 70, 70′, 70″reviews the preliminary report 101 and any associated images senttherewith and then prepares a final estimate 102, 102′, 102″. The finalestimate 102, 102′, 102″ is then mailed, emailed or faxed to thecustomer 90 or back to the estimating entity 130. The estimating entity130 then sends the final estimate 102, 102′, 102″ to the customer 90. Inthis embodiment, the estimating entity 130 includes a computer 135 inwhich the roof estimating software program 50″ is loaded into itsworking memory 136 loaded and linked to the aerial image database 52″containing image files 54″. An optional calibration module 56″ may beloaded into the working memory 136 of the computer 135.

FIGS. 5A-5F are individual pages that make up a representative report.In FIG. 5A, a cover page 103 that lists the address 103 a of a building103 c and an overhead aerial image 103 b of the building 103 c. In FIG.5B, a second page 104 of the report is shown that shows two wideoverhead perspective views 104 a and 104 b of the building 103 c at theaddress with the surrounding areas more clearly shown. FIG. 5C is thethird page 105 of the report which shows a line drawing 105 a of thebuilding showing ridge and valley lines, dimensions and a compassindicator. FIG. 5D is an illustration of the fourth page 106 of thereport showing a line drawing 106 a of the building showing the pitch ofeach roof section along with a compass indicator. The pitch in thisexample is given in inches, and it represents the number of verticalinches that the labeled planar roof section drops over 12 inches ofhorizontal run. The slope can be easily calculated from such arepresentation using basic trigonometry. The use of a numerical value ofinches of rise per foot of run is a well known measure of slope in theroofing industry. A roof builder typically uses this information toassist in the repair and/or construction of a roof. Of course, othermeasures and/or units of slope may be utilized as well, includingpercent grade, angle in degrees, etc. FIG. 5E is an illustration of thefifth page 107 of the report showing a line drawing 107 a of thebuilding showing the square footage of each roof section along with thetotal square foot area value. FIG. 5F is an illustration of a sixth page108 of the report showing a line drawing 108 a of the building wherenotes or comments may be written.

Using the above roof estimation system, a detailed description of howthe system may be used in one example embodiment is now provided.

First, a property of interest is identified by a potential customer ofthe roof estimation service 70. The customer may be a property owner, aroof construction/repair company, a contractor, an insurance company, asolar panel installer, etc. The customer contacts the roof estimationservice with the location of the property. Typically, this will be astreet address. The roof estimation service 70 may then use a geo-codingprovider, operated by the service 70 or some third party, to translatethe location information (such as a street address) into a set ofcoordinates that can be used to query an aerial or satellite imagedatabase. Typically, the geo-coding provider will be used to translatethe customer supplied street address into a set of longitude-latitudecoordinates.

Next, the longitude-latitude coordinates of the property may be used toquery an aerial and/or satellite imagery database in order to retrieveone or more images of the property of interest. It is important to notethat horizontal (non-sloping) flat roofs only require a single image ofthe property. However, few roofs (especially those on residentialbuildings) are horizontally flat, and often contain one or more pitchedsections. In such cases, two or more photographs are typically used inorder for the service 70 to identify and measure all relevant sectionsand features of the roof.

Once the images of the roof section of the building are obtained, atleast one of the images may be calibrated. During calibration, thedistance in pixels between two points on the image is converted into aphysical length. This calibration information is typically presented asa scale marker on the image itself, or as additional informationsupplied by the image database provider along with the requested image.

The image(s) and calibration information returned by the imagerydatabase is entered or imported into measurement software of the service70.

Next, a set of reference points may be identified in each of the images.The service's 70 measurement software then uses these reference pointsand any acceptable algorithm to co-register the images and reconstructthe three-dimensional geometry of the object identified by the referencepoints. There are a variety of photo-grammetric algorithms that can beutilized to perform this reconstruction. One such algorithm used by theservice 70 uses photographs taken from two or more view points to“triangulate” points of interest on the object in three-dimensional(“3D”) space. This triangulation can be visualized as a process ofprojecting a line originating from the location of the photograph'sobservation point that passes through a particular reference point inthe image. The intersection of these projected lines from the set ofobservation points to a particular reference point identifies thelocation of that point in 3D space. Repeating the process for all suchreference points allows the software to build a 3D model of thestructure.

The optimal choice of reconstruction algorithm depends on a number offactors such as the spatial relationships between the photographs, thenumber and locations of the reference points, and any assumptions thatare made about the geometry and symmetry of the object beingreconstructed. Several such algorithms are described in detail intextbooks, trade journals, and academic publications.

Once the reconstruction of the building is complete, the results may bereviewed for completeness and correctness. If necessary, an operator ofthe service's 70 software will make corrections to the reconstructedmodel.

Information from the reconstructed model may then be used to generate areport containing information relevant to the customer. The informationin the report may include total square footage, square footage and pitchof each section of roof, linear measurements of all roof segments,identification and measurement of ridges and valleys, and differentelevation views rendered from the 3D model (top, side, front, etc).

Using the above description, a method for estimating the size and therepair or replacement costs of a roof may include the following steps:

a. selecting a roof estimation system that includes a computer with aroof estimation software program loaded into its working memory, saidroof estimation software uses aerial image files of buildings in aselected region and a calibration module that allows the size, geometry,and orientation of a roof section to be determined from said aerialimage files;

b. submitting a request for a measurement of a roof of a building at aknown location;

c. submitting the location information of a building with a roof thatneeds a size determination, a repair estimate, or replacement estimate;

d. entering the location information of said building and obtainingaerial image files of one or more roof sections used on a roof; and,

e. using said calibration module to determine the size, geometry andpitch of each said roof section.

In the above method, the entity requesting the measurement may be a roofconstruction/repair company, the building tenant, the building owner, aninsurance company, etc.

FIG. 6 is a block diagram illustrating example functional elements ofone embodiment of a roof estimation system. In particular, FIG. 6 showsan example Roof Estimation System (“RES”) 600 comprising an imageacquisition engine 601, a roof modeling engine 602, a report generationengine 603, image data 605, model data 606, and report data 607. The RES600 is communicatively coupled to an image source 610, a customer 615,and optionally an operator 620. The RES 600 and its components may beimplemented as part of a computing system, as will be further describedwith reference to FIG. 7.

In the illustrated embodiment, the RES 600 performs some or all of thefunctions of the whole system described with reference to FIGS. 1 and 2,and also additional functions as described below. For example, the RES600 may perform one or more of the functions of the software program 50,the roof estimating entity 105, the aerial image file database 52,and/or the calibration module 56.

More specifically, in the illustrated embodiment of FIG. 6, the RES 600is configured to generate a roof estimate report 632 for a specifiedbuilding, based on aerial images 631 of the building received from theimage source 610. The image source 610 may be any provider of images ofthe building for which a roof estimate is being generated. In oneembodiment, the image source 610 includes a computing system thatprovides access to a repository of aerial images of one or morebuildings. The image acquisition engine 601 obtains one or more aerialimages of the specified building by, for example, providing an indicatorof the location of the specified building (e.g., street address, GPScoordinates, lot number, etc.) to the image source 610. In response, theimage source 610 provides to the image acquisition engine 605 the one ormore aerial images of the building. The image acquisition engine 601then stores the received aerial images as image data 605, for furtherprocessing by other components of the RES 600. In some embodiments, theaerial images may include images obtain via one or more ground-basedplatforms, such as a vehicle-mounted camera that obtains street-levelimages of buildings, a nearby building, a hilltop, etc. In some cases, avehicle-mounted camera may be mounted in an elevated position, such as aboom.

Next, the roof modeling engine 602 generates a model of the roof of thespecified building. In the illustrated embodiment, the roof modelingengine 602 generates a three-dimensional model, although in otherembodiments, a two-dimensional (e.g., top-down roof plan) may begenerated instead or in addition. As noted above, a variety of automaticand semi-automatic techniques may be employed to generate a model of theroof of the building. In one embodiment, generating such a model isbased at least in part on a correlation between at least two of theaerial images of the building. For example, the roof modeling engine 602receives an indication of a corresponding feature that is shown in eachof the two aerial images. In one embodiment, an operator 620, viewingtwo or more images of the building, inputs an indication in at leastsome of the images, the indications identifying which points of theimages correspond to each other for model generation purposes.

The corresponding feature may be, for example, a vertex of the roof ofthe building, the corner of one of the roof planes of the roof, a pointof a gable or hip of the roof, etc. The corresponding feature may alsobe a linear feature, such as a ridge or valley line between two roofplanes of the roof. In one embodiment, the indication of a correspondingfeature on the building includes “registration” of a first point in afirst aerial image, and a second point in a second aerial image, thefirst and second points corresponding the substantially the same pointon the roof of the building. Generally, point registration may includethe identification of any feature shown in both aerial images. Thus, thefeature need not be a point on the roof of the building. Instead, it maybe, for example, any point that is visible on both aerial images, suchas on a nearby building (e.g., a garage, neighbor's building, etc.), ona nearby structure (e.g., swimming pool, tennis court, etc.), on anearby natural feature (e.g., a tree, boulder, etc.), etc.

In some embodiments, the roof modeling engine 602 determines thecorresponding feature automatically, such as by employing on one or moreimage processing techniques used to identify vertexes, edges, or otherfeatures of the roof. In other embodiments, the roof modeling engine 602determines the corresponding feature by receiving, from the humanoperator 620 as operator input 633, indications of the feature shown inmultiple images of the building.

In addition, generating a 3D model of the roof of a building may includecorrecting one or more of the aerial images for various imperfections.For example, the vertical axis of a particular aerial image sometimeswill not substantially match the actual vertical axis of its scene. Thiswill happen, for example, if the aerial images were taken at differentdistances from the building, or at a different pitch, roll, or yawangles of the aircraft from which the images were produced. In suchcases, an aerial image may be corrected by providing the operator 620with a user interface control operable to adjust the scale and/orrelative angle of the aerial image to correct for such errors. Thecorrection may be either applied directly to the aerial image, orinstead be stored (e.g., as an offset) for use in model generation orother functions of the RES 600.

Generating a 3D model of the roof of a building further includes theautomatic or semi-automatic identification of features of the roof ofthe building. In one embodiment, one or more user interface controls maybe provided, such that the operator 620 may indicate (e.g., draw, paint,etc.) various features of the roof, such as valleys, ridges, hips,vertexes, planes, edges, etc. As these features are indicated by theoperator 620, a corresponding 3D model may be updated accordingly toinclude those features. These features are identified by the operatorbased on a visual inspection of the images and by providing inputs thatidentify various features as valleys, ridges, hips, etc. In some cases,a first and a second image view of the roof (e.g., a north and eastview) are simultaneously presented to the operator 620, such that whenthe operator 620 indicates a feature in the first image view, aprojection of that feature is automatically presented in the secondimage view. By presenting a view of the 3D model, simultaneouslyprojected into multiple image views, the operator 620 is provided withuseful visual cues as to the correctness of the 3D model and/or thecorrespondence between the aerial images.

In addition, generating a 3D model of the roof of a building may includedetermining the pitch of one or more of the sections of the roof. Insome embodiments, one or more user interface controls are provided, suchthat the operator 620 may accurately determine the pitch of each of theone or more roof sections. An accurate determination of the roof pitchmay be employed (by a human or the RES 600) to better determine anaccurate cost estimate, as roof sections having a low pitch aretypically less costly surfaces to repair and/or replace.

The generated 3D model typically includes a plurality of planar roofsections that each correspond to one of the planar sections of the roofof the building. Each of the planar roof sections in the model has anumber of associated dimensions and/or attributes, among them slope,area, and length of each edge of the roof section. Other information mayinclude, whether a roof section edge is in a valley or on a ridge of theroof, the orientation of the roof section, and other informationrelevant to roof builder (e.g., roof and/or roof section perimeterdimensions and/or outlines). Once a 3D model has been generated to thesatisfaction of the roof modeling engine 602 and/or the operator 620,the generated 3D model is stored as model data 606 for furtherprocessing by the RES 600. In one embodiment, the generated 3D model isthen stored in a quality assurance queue, from which it is reviewed andpossibly corrected by a quality control operator.

The report generation engine 603 generates a final roof estimate reportbased on a 3D model stored as model data 606, and then stores thegenerated report as report data 607. Such a report typically includesone or more plan (top-down) views of the 3D model, annotated withnumerical values for the slope, area, and/or lengths of the edges of atleast some of the plurality of planar roof sections of the 3D model ofthe roof. For example, the example report of FIGS. 5A-5E includesmultiple plan views of a generated 3D model of the house 103 c. Inparticular, FIG. 5C shows a first plan view of the 3D model, annotatedwith dimensions of the edges of each roof section. FIG. 5D shows asecond plan view of the same 3D model, annotated with the slope of eachroof section. FIG. 5E shows a third plan view of the same 3D model,annotated with the area of each roof section.

In some embodiments, generating a report includes labeling one or moreviews of the 3D model with annotations that are readable to a humanuser. Some 3D models include a large number of small roof details, suchas dormers or other sections, such that applying uniformly sized,oriented, and positioned labels to roof section views results in avisually cluttered diagram. Accordingly, various techniques may beemployed to generate a readable report, including automaticallydetermining an optimal or near-optimal label font size, label position,and/or label orientation, such that the resulting report may be easilyread and understood by the customer 615.

In addition, in some embodiments, generating a report includesautomatically determining a cost estimate, based on specified costs,such as those of materials, labor, transportation, etc. For example, thecustomer 615 provides indications of material and labor costs to the RES600. In response, the report generation engine 603 generates a roofestimate report that includes a cost estimate, based on the costsprovided by the customer 615 and the attributes of the particular roof,such as area, pitch, etc.

In one embodiment, the generated report is then provided to a customer.The generated report can be represented, for example, as an electronicfile (e.g., a PDF file) or a paper document. In the illustrated example,roof estimate report 632 is transmitted to the customer 615. Thecustomer 615 may be or include any human, organization, or computingsystem that is the recipient of the roof estimate report 632. Thecustomer 615 may be a property owner, a property manager, a roofconstruction/repair company, a general contractor, an insurance company,a solar power panel installer, etc. Reports may be transmittedelectronically, such as via a network (e.g., as an email, Web page,etc.) or by some shipping mechanism, such as the postal service, acourier service, etc.

In some embodiments, one or more of the 3D models stored as model data606 are provided directly to the customer, without first beingtransformed into a report. For example, a 3D model may be exported as adata file, in any acceptable format, that may be consumed or otherwiseutilized by some other computing system, such as computer-aided design(“CAD”) tool, drawing program, etc.

FIG. 7 is an example block diagram of a computing system for practicingembodiments of a roof estimation system. FIG. 7 shows a computing system700 that may be utilized to implement a Roof Estimation System (“RES”)710. One or more general purpose or special purpose computing systemsmay be used to implement the RES 710. More specifically, the computingsystem 700 may comprise one or more distinct computing systems presentat distributed locations. In addition, each block shown may representone or more such blocks as appropriate to a specific embodiment or maybe combined with other blocks. Moreover, the various blocks of the RES710 may physically reside on one or more machines, which use standardinter-process communication mechanisms (e.g., TCP/IP) to communicatewith each other. Further, the RES 710 may be implemented in software,hardware, firmware, or in some combination to achieve the capabilitiesdescribed herein.

In the embodiment shown, computing system 700 comprises a computermemory (“memory”) 701, a display 702, one or more Central ProcessingUnits (“CPU”) 703, Input/Output devices 704 (e.g., keyboard, mouse, CRTor LCD display, and the like), other computer-readable media 705, andnetwork connections 706. The RES 710 is shown residing in memory 701. Inother embodiments, some portion of the contents, some of, or all of thecomponents of the RES 710 may be stored on and/or transmitted over theother computer-readable media 705. The components of the RES 710preferably execute on one or more CPUs 703 and generate roof estimatereports, as described herein. Other code or programs 730 (e.g., a Webserver, a database management system, and the like) and potentiallyother data repositories, such as data repository 720, also reside in thememory 710, and preferably execute on one or more CPUs 703. Not all ofthe components in FIG. 7 are required for each implementation. Forexample, some embodiments embedded in other software do not providemeans for user input, for display, for a customer computing system, orother components.

In a typical embodiment, the RES 710 includes an image acquisitionengine 711, a roof modeling engine 712, a report generation engine 713,an interface engine 714, and a roof estimation system data repository716. Other and/or different modules may be implemented. In addition, theRES 710 interacts via a network 750 with an image source computingsystem 755, an operator computing system 765, and/or a customercomputing system 760.

The image acquisition engine 711 performs at least some of the functionsof the image acquisition engine 601 described with reference to FIG. 6.In particular, the image acquisition engine 711 interacts with the imagesource computing system 755 to obtain one or more images of a building,and stores those images in the RES data repository 716 for processing byother components of the RES 710. In some embodiments, the imageacquisition engine 711 may act as an image cache manager, such that itpreferentially provides images to other components of the RES 710 fromthe RES data repository 716, while obtaining images from the imagesource computing system 755 when they are not already present in the RESdata repository 716.

The roof modeling engine 712 performs at least some of the functions ofthe roof modeling engine 602 described with reference to FIG. 6. Inparticular, the roof modeling engine 712 generates a 3D model based onone or more images of a building that are obtained from the RES datarepository 716. As noted, 3D model generation may be performedsemi-automatically, based on at least some inputs received from thecomputing system 765. In addition, at least some aspects of the 3D modelgeneration may be performed automatically, based on image processingand/or image understanding techniques. After the roof modeling engine712 generates a 3D model, it stores the generated model in the RES datarepository 716 for further processing by other components of the RES710.

The report generation engine 713 performs at least some of the functionsof the report generation engine 603 described with reference to FIG. 6.In particular, the report generation engine 713 generates roof reportsbased on 3D models stored in the RES data repository 716. Generating aroof report may include preparing one or more views of a given 3D modelof a roof, annotating those views with indications of variouscharacteristics of the model, such as dimensions of sections or otherfeatures (e.g., ridges, valleys, etc.) of the roof, slopes of sectionsof the roof, areas of sections of the roof, etc.

The interface engine 714 provides a view and a controller thatfacilitate user interaction with the RES 710 and its various components.For example, the interface engine 714 provides an interactive graphicaluser interface that can be used by a human user operating the operatorcomputing system 765 to interact with, for example, the roof modelingengine 612, to perform functions related to the generation of 3D models,such as point registration, feature indication, pitch estimation, etc.In other embodiments, the interface engine 714 provides access directlyto a customer operating the customer computing system 760, such that thecustomer may place an order for a roof estimate report for an indicatedbuilding location. In at least some embodiments, access to thefunctionality of the interface engine 714 is provided via a Web server,possibly executing as one of the other programs 730.

In some embodiments, the interface engine 714 provides programmaticaccess to one or more functions of the RES 710. For example, theinterface engine 714 provides a programmatic interface (e.g., as a Webservice, static or dynamic library, etc.) to one or more roof estimationfunctions of the RES 710 that may be invoked by one of the otherprograms 730 or some other module. In this manner, the interface engine714 facilitates the development of third-party software, such as userinterfaces, plug-ins, adapters (e.g., for integrating functions of theRES 710 into desktop applications, Web-based applications, embeddedapplications, etc.), and the like. In addition, the interface engine 714may be in at least some embodiments invoked or otherwise accessed viaremote entities, such as the operator computing system 765, the imagesource computing system 755, and/or the customer computing system 760,to access various roof estimation functionality of the RES 710.

The RES data repository 716 stores information related the roofestimation functions performed by the RES 710. Such information mayinclude image data 605, model data 606, and/or report data 607 describedwith reference to FIG. 6. In addition, the RES data repository 716 mayinclude information about customers, operators, or other individuals orentities associated with the RES 710.

In an example embodiment, components/modules of the RES 710 areimplemented using standard programming techniques. For example, the RES710 may be implemented as a “native” executable running on the CPU 703,along with one or more static or dynamic libraries. In otherembodiments, the RES 710 is implemented as instructions processed byvirtual machine that executes as one of the other programs 730. Ingeneral, a range of programming languages known in the art may beemployed for implementing such example embodiments, includingrepresentative implementations of various programming languageparadigms, including but not limited to, object-oriented (e.g., Java,C++, C#, Visual Basic.NET, Smalltalk, and the like), functional (e.g.,ML, Lisp, Scheme, and the like), procedural (e.g., C, Pascal, Ada,Modula, and the like), scripting (e.g., Perl, Ruby, Python, JavaScript,VBScript, and the like), declarative (e.g., SQL, Prolog, and the like).

The embodiments described above may also use well-known synchronous orasynchronous client-server computing techniques. However, the variouscomponents may be implemented using more monolithic programmingtechniques as well, for example, as an executable running on a singleCPU computer system, or alternatively decomposed using a variety ofstructuring techniques known in the art, including but not limited to,multiprogramming, multithreading, client-server, or peer-to-peer,running on one or more computer systems each having one or more CPUs.Some embodiments execute concurrently and asynchronously, andcommunicate using message passing techniques. Equivalent synchronousembodiments are also supported by an RES implementation. Also, otherfunctions could be implemented and/or performed by eachcomponent/module, and in different orders, and by differentcomponents/modules, yet still achieve the functions of the RES.

In addition, programming interfaces to the data stored as part of theRES 710, such as in the RES data repository 716, can be available bystandard mechanisms such as through C, C++, C#, and Java APIs; librariesfor accessing files, databases, or other data repositories; throughscripting languages such as XML; or through Web servers, FTP servers, orother types of servers providing access to stored data. For example, theRES data repository 716 may be implemented as one or more databasesystems, file systems, memory buffers, or any other technique forstoring such information, or any combination of the above, includingimplementations using distributed computing techniques.

Also, the example RES 710 can be implemented in a distributedenvironment comprising multiple, even heterogeneous, computer systemsand networks. For example, in one embodiment, the image acquisitionengine 711, the roof modeling engine 712, the report generation engine713, the interface engine 714, and the data repository 716 are alllocated in physically different computer systems. In another embodiment,various modules of the RES 710 are hosted each on a separate servermachine and are remotely located from the tables which are stored in thedata repository 716. Also, one or more of the modules may themselves bedistributed, pooled or otherwise grouped, such as for load balancing,reliability or security reasons. Different configurations and locationsof programs and data are contemplated for use with techniques ofdescribed herein. A variety of distributed computing techniques areappropriate for implementing the components of the illustratedembodiments in a distributed manner including but not limited to TCP/IPsockets, RPC, RMI, HTTP, Web Services (XML-RPC, JAX-RPC, SOAP, and thelike).

Furthermore, in some embodiments, some or all of the components of theRES are implemented or provided in other manners, such as at leastpartially in firmware and/or hardware, including, but not limited to oneor more application-specific integrated circuits (ASICs), standardintegrated circuits, controllers (e.g., by executing appropriateinstructions, and including microcontrollers and/or embeddedcontrollers), field-programmable gate arrays (FPGAs), complexprogrammable logic devices (CPLDs), and the like Some or all of thesystem components and/or data structures may also be stored (e.g., assoftware instructions or structured data) on a computer-readable medium,such as a hard disk, a memory, a network, or a portable media article tobe read by an appropriate drive or via an appropriate connection. Thesystem components and data structures may also be stored as data signals(e.g., by being encoded as part of a carrier wave or included as part ofan analog or digital propagated signal) on a variety ofcomputer-readable transmission mediums, which are then transmitted,including across wireless-based and wired/cable-based mediums, and maytake a variety of forms (e.g., as part of a single or multiplexed analogsignal, or as multiple discrete digital packets or frames). Suchcomputer program products may also take other forms in otherembodiments. Accordingly, embodiments of this disclosure may bepracticed with other computer system configurations.

FIG. 8 is an example flow diagram of a first example roof estimationroutine provided by an example embodiment. The illustrated routine 800may be provided by, for example, execution of the roof estimation system710 described with respect to FIG. 7. The illustrated routine 800generates a 3D model of a roof of a building, based on two or moreaerial images of the building, and further prepares and transmits a roofestimate report based on the 3D model.

More specifically, the routine begins at step 801 where it receives afirst and a second aerial image of a building, each of the aerial imagesproviding a different view of the roof of the building. The aerialimages may be received from, for example, the image source computingsystem 755 and/or from the RES data repository 716 described withreference to FIG. 7. As discussed above, aerial images may be originallycreated by cameras mounted on airplanes, balloons, satellites, etc. Insome embodiments, images obtained from ground-based platforms (e.g.,vehicle-mounted cameras) may be used instead or in addition.

In step 802, the routine correlates the first aerial image with thesecond aerial image. In some embodiments, correlating the aerial imagesmay include registering pairs of points on the first and second aerialimages, each pair of points corresponding to substantially the samepoint on the roof depicted in each of the images. Correlating the aerialimages may be based at least in part on input received from a humanoperator and/or automatic image processing techniques.

In step 803, the routine generates, based at least in part on thecorrelation between the first and second aerial images, athree-dimensional model of the roof. The three-dimensional model of theroof may include a plurality of planar roof sections that each have acorresponding slope, area, and perimeter. Generating thethree-dimensional model may be based at least in part indications offeatures of the roof, such as valleys, ridges, edges, planes, etc.Generating the three-dimensional model may also be based at least inpart on input received from a human operator (e.g., indications of roofridges and valleys) and/or automatic image processing techniques.

In step 804, the routine prepares (e.g., generates, determines,produces, etc.) and transmits a roof estimate report that includes oneor more annotated top-down views of the three-dimensional model. In someembodiments, the annotations include numerical values indicating theslope, area, and lengths of the edges of the perimeter of at least someof the plurality of planar roof sections of the three-dimensional modelof the roof. The roof estimate report may be an electronic file thatincludes images of the building and/or its roof, as well as linedrawings of one or more views of the three-dimensional model of thebuilding roof. Preparing the report may include annotating the reportwith labels that are sized and oriented in a manner that preservesand/or enhances readability of the report. For example, labels on aparticular line drawing may be sized based at least in part on the sizeof the feature (e.g., roof ridge line) that they are associated with,such that smaller features are annotated with smaller labels so as topreserve readability of the line drawing by preventing or reducing theoccurrence of labels that overlap with other portions (e.g., lines,labels, etc.) of the line drawing. The roof estimate report may betransmitted to various destinations, such as directly to a customer orcomputing system associated with that customer, a data repository,and/or a quality assurance queue for inspection and/or improvement by ahuman operator.

After step 804, the routine ends. In other embodiments, the routine mayinstead return to step 801, to generate another roof estimate report foranother building. Note that the illustrated routine may be performedinteractively, such as based at least in part on one or more inputsreceived from a human operator, or in batch mode, such as for performingautomatic, bulk generation of roof estimate reports.

FIG. 9 is an example flow diagram of a second example roof estimationroutine provided by an example embodiment. The illustrated routine 900may be provided by, for example, execution of the roof estimation system710 described with respect to FIG. 7. The illustrated routine 900generates a roof estimate report based on a single aerial image andadditional information received from a user, such as information aboutthe pitch of various roof sections.

In step 901, the routine receives a substantially top-down aerial imageof a building having a roof. Such an aerial image may be obtained from,for example, a satellite or aircraft.

In step 902, the routine generates a preliminary model of the roof basedon the received aerial image. The preliminary roof model may be atwo-dimensional (“flat”) model that includes information about theperimeter of the roof and at least some of its corresponding planar roofsections. Such a preliminary roof model may include estimates of variousdimensions of the roof, such as edge lengths and/or section areas. Insome cases, the preliminary roof model does not include informationrelated to the pitch of various roof sections.

In step 903, the routine modifies the preliminary model based onadditional information about the roof received from a user. For example,the preliminary model may be presented to a user (e.g., a customer, anoperator, etc.), by displaying a representation of the model, such as aline drawing. In response, the user provides the routine with pitchinformation and/or feature identification (e.g., of ridges and/orvalleys), etc. Such user-supplied information is then incorporated intothe preliminary roof model to obtain a modified (refined) roof model. Insome cases, the user supplies the additional information via a Web-baseinterface that provides access to the routine.

In step 904, the routine prepares and transmits a roof estimate reportthat includes one or more annotated views of the modified model. Asdiscussed above, the annotations may include numerical values indicatingthe slope, area, and lengths of the edges of the perimeter of at leastsome of the roof sections of the roof. After step 904, the routine ends.

The routines 800 and 900 may be used in conjunction to advantageouslyoffer customers roof estimate reports at differing price points. Forexample, routine 800 can be utilized as part of a “premium” service thatoffers a customer with a more accurate roof estimate report for minimaleffort on the customer's part. Routine 900 can be utilized as part of an“economy” service that offers a customer a less accurate roof estimatereport at a lower price, but that may be further refined with additionaleffort from the customer.

From the foregoing it will be appreciated that, although specificembodiments have been described herein for purposes of illustration,various modifications may be made without deviating from the spirit andscope of the present disclosure. For example, the methods, systems, andtechniques for generating and providing roof estimate reports discussedherein are applicable to other architectures other than the illustratedarchitecture or a particular roof estimation system implementation.Also, the methods and systems discussed herein are applicable todiffering network protocols, communication media (optical, wireless,cable, etc.) and devices (such as wireless handsets, electronicorganizers, personal digital assistants, portable email machines, gamemachines, pagers, navigation devices such as GPS receivers, etc.).Further, the methods and systems discussed herein may be utilized byand/or applied to other contexts or purposes, such as by or for solarpanel installers, roof gutter installers, awning companies, HVACcontractors, general contractors, and/or insurance companies.

1. A computer-implemented method for generating a roof estimate report,the method comprising: receiving a first aerial image of a buildinghaving the roof; receiving a second aerial image of the building havingthe roof, the first and second aerial images of the building having beentaken independent of each other, the first and second aerial images ofthe building providing different views of the roof from each other;calibrating at least one of the first and second aerial images of thebuilding using calibration information received from a calibrationmodule; correlating, without using a preexisting three-dimensional modelof the building, the first aerial image of the building with the secondaerial image of the building, the correlating including registeringpairs of points on the first and second aerial images of the building,each pair of points corresponding to a same point on the roof depictedin each of the first and second aerial images of the building;generating, without using a preexisting three-dimensional model of thebuilding, based at least in part on the correlation of the first andsecond aerial images of the building, a three-dimensional model of theroof that includes a plurality of planar roof sections that each have acorresponding pitch, area, and edges; determining a pitch of a pluralityof sections of the roof; and generating a roof estimate report thatincludes at least one top plan view of the three-dimensional modelannotated with numerical indications of the determined pitch.